home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19981211-19990422
/
000202_news@watsun.cc.columbia.edu _Tue Feb 9 21:53:55 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@watsun.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id VAA14940
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 9 Feb 1999 21:53:49 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id VAA13648
for kermit.misc@watsun.cc.columbia.edu; Tue, 9 Feb 1999 21:25:00 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: brad.de.groot@gecits-ap.com
Subject: Re: Help: Transmitting to Kermit TSO 4.3.2
Date: Wed, 10 Feb 1999 02:25:41 GMT
Organization: Customer of OzEmail/Access One Pty Ltd, Melbourne, Australia
Message-ID: <36c0ecc4.16634566@news.aone.com.au>
To: kermit.misc@mailrelay2.cc.columbia.edu
Thanks for your help guys but I have still not been able to rectify
the problem.
I actually replicatated the ATOE, ETOA, TATOE and TETOA tables to
match our previous working version of Kermit-TSO. My reson for doing
this is that I thought if I could get the tables to match the old
version of Kermit-TSO then it should work in the new version of
Kermit-TSO 4.3.2.
Am I correct in thinking this?
Do you have any other sugestions that I could try to get this working.
Thanks,
Brad
On 12 Jan 1999 17:49:05 GMT, pepmnt@watsun.cc.columbia.edu (John
Chandler) wrote:
>Frank da Cruz (fdc@watsun.cc.columbia.edu) wrote:
>: In article <369a9176.10188882@news.ozemail.com.au>,
>: <brad.de.groot@gecits-ap.com> wrote:
>: : I previously had Kermit TSO 4.0 and have upgraded to Kermit TSO
>: : 4.3.2.
>
>Note that 4.0 was not a production release of TSO Kermit. If you had it
>working, it must have been considerably modified.
>
>: : I was sending the file at a speed of 9600.
>
>The SPEED setting in Kermit-370 has nothing to do with success or failure,
>but is used only for the purpose of computing the throughput efficiency.
>
>: Checksum errors can be caused by data corruption or data loss. This is
>: why we have checksums in the first place.
>
>: But in the IBM mainframe world, which uses parity, they can also be caused
>: by a parity mismatch. Make sure your client program is set to use the same
>: parity (even, mark, etc) that the mainframe (or its front end) expects.
>
>If your connection to the mainframe is in line mode, i.e., if TSO Kermit
>says "Controller is TTY" or "Controller is VTAMTTY", then the most likely
>cause of your problem is a mismatch between the ASCII/EBCDIC translation
>tables used by the system (VTAM or whatever) and by Kermit. The corrective
>action is to make the tables agree, most likely by installing a
>SYS1.KERMINI or, if need be, by modifying Kermit itself. This procedure is
>described in some detail in the user's guide for TSO Kermit.
>
> John Chandler